CVE-2026-8925
SASL double-free
Description
The curl logic that works with SASL authentication could end up cleaning up the GSASL context *twice* without clearing the pointer in between, making it `free()` the same pointer twice.
INFO
Published Date :
July 3, 2026, 6:15 a.m.
Last Modified :
July 3, 2026, 6:15 a.m.
Remotely Exploit :
No
Source :
curl
Affected Products
The following products are affected by CVE-2026-8925
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Ensure GSASL context pointer is cleared after the first free.
- Review curl's SASL authentication logic for pointer management.
- Apply patches to correct double-free vulnerabilities.
- Test thoroughly to confirm the fix.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-8925 vulnerability anywhere in the article.